In spite of strong conceptual arguments for the value of strategic data planning as a means to increase data integration in large organizations, empirical research has found more evidence of problems than of success. In this paper, four detailed case studies of SDP efforts, along with summaries of five previously reported efforts, are analyzed. Fifteen specific propositions are offered, with two overall conclusions. The first conclusion is that SDP, though conceived of as a generally appropriate method, may not be the best planning approach in all situations. The second conclusion is that the SDP method of analyzing business functions and their data requirements may not be the best way to develop a "data architecture," given the required level of commitment of talented individuals, the cost, the potential errors, and the high level of abstraction of the result. These lessons can aid practitioners in deciding when to use SDP and guide them as they begin the process of rethinking and modifying the SDP to be more effective.
For many organizations, the ability to make coordinated, organization-wide responses to today's business problems is thwarted by the lack of data integration or commonly defined data elements and codes across different information systems. Though many researchers and practitioners have implicitly assumed that data integration always results in net benefits to an organization, this article questions that view. Based on theories of organizational information processing, a model of the impact of data integration is developed that includes gains in organization-wide coordination and organization-wide decision making, as well as losses in local autonomy and flexibility, and changes in system design and implementation costs. The importance of each of these impacts is defended by theoretical arguments and illustrated by case examples. This model suggests that the benefits of data integration will outweigh costs only under certain situations, and probably not for all the data the organization uses. Therefore, MIS researchers and practitioners should consider the need for better conceptualization and methods for implementing "partial integration" in organizations.